List of Exception Codes

The following is a list of active exception codes, including subcheck exception codes, for the associated Quality Control (QC Quality Control) check. Click the quality control check name in the list to view a description of the check. For information on turning on exception codes and subcheck exception codes, see Exception Code Basics.

Attribute QC Checks

**Table 1.** Attribute quality control checks and exception codes
Quality Control Check	Exception Code
Acceptable Values	101
Address Range Overlaps	103
Duplicate Values	112 The 402 exception code is no longer supported. Duplicate attribution on address points used for Next Generation purposes is not recommended. If an exception code is absolutely required, use exception code 112 for this QC check.
Exception Code Formatting	006
Field Comparison	302
Line to Polygon Attribute Compare	113
Null Value in Field	100
Point to Polygon Attribute Compare	308
Unacceptable Values	307

Geometry QC Checks

**Table 2.** Geometry quality control checks and exception codes
Quality Control Check	Exception Code
Complex Geometry	004
Empty Geometry	005
Features Not Split at Polygon	201
Features Outside of Polygon	603
Multipart Geometry	003
Polygon - Multi-Layer Gap	602
Polygon - Multi-Layer Overhang	604
Polygon - Single Layer Gap	600
Polygon - Single Layer Overlap	601
Segment Snapped to Adjacent Segment - Same Layer	200

Ingest Validation

**Table 3.** Ingest Validation quality control checks and exception codes
Quality Control Check	Exception Code
Roads Need Zero Ranges	701 and 702

Synchronization QC Checks

**Table 4.** Synchronization quality control checks and exception codes
Quality Control Check	Exception Code
ALI to RCL Synchronization	851
ALI to SSAP Synchronization	801
MSAG to RCL Synchronization	901
SSAP to MSAG Synchronization	306
SSAP to RCL Synchronization	401

Synchronization QC Checks - Subchecks and Exception Codes

Exception codes used in Synchronization QC checks should always be applied to the main layer or table being inspected.

For example, to exclude a feature from the Site/Structure Address Point (SSAP) to RCL Synchronization check, apply the exception code to the address point, not the road centerline. For ALI to RCL Synchronization checks, apply the exception code to the ALI record, not the road centerline. Placing an exception code on the referencing layer will not have any negative consequences, but will not create the preferred behavior.

The synchronization QC checks run a series of subchecks and prioritizes higher-impact data issues. This approach flags the most critical problems first and provides clear, actionable feedback to help you to quickly clean up your data.

ALI to RCL Synchronization Subchecks

The ALI to RCL Synchronization QC subchecks are completed in the following order.

**Table 5**. ALI to RCL quality control subchecks and exception codes.
Order	Subcheck Description	Exception Code
1.	Address number is missing or invalid. This subcheck searches for a valid ALI address number.	852
2.	Address number fully matches multiple road segments. This subcheck searches for an ALI address number that fully matches multiple road segments—the address number, street full name, community, and ESN Emergency Service Number. A three to five digit number representing a unique combination of emergency service agencies (law enforcement, fire and emergency medical service) designated to serve a specific range of addresses within a particular geographical area, or Emergency Service Zone (ESZ). The ESN facilitates selective routing and selective transfer, if required, to the appropriate PSAP and dispatching of the proper service agency(ies). are an exact match.	862
3.	Address can be placed on both the left and right side of the corresponding road segment. This subcheck searches for an ALI address number that fully matches both the left and right side of the same roadcenterline—the address number, street full name, community, and ESN are an exact match.	861
4.	No matching full street name found between the ALI record and the road segment. This subcheck identifies when no street full name match is found.	853
5.	Address only corresponds to road segment with zero or missing ranges. This subcheck identifies when a street full name match is found, but only to roads with zero, empty string, or null range values.	854
6.	Address number is lower than all corresponding road ranges. This subcheck identifies when a street full name match is found, but only to roads with address range values larger than the ALI's address number.	855
7.	Address number is higher than all corresponding road ranges. This subcheck identifies when a street full name match is found, but only to roads with address range values smaller than the ALI's address number.	856
8.	Address number parity does not match the corresponding road segments. This subcheck identifies when a street full name match is found, and the ALI address number is within the road's ranges, but only to road records with the incorrect parity values.	863
9.	Address only corresponds to a road segment with a different ESN, but matching community. This subcheck identifies when an ALI record's ESN value does not match the corresponding road segment.	860
10.	Address only corresponds to a road segment with a different community, but matching ESN. This subcheck identifies when a Street Full Name, Address Number, Parity, and ESN match is found, but only to records with mismatching Community values.	859
11.	Address only corresponds to a road segment with a different community and ESN. This subcheck identifies when an ALI record's ESN and community values do not match the road corresponding segment.	858
12.	Address AdNumPre value does not match the road segment. This subcheck identifies when an ALI's address number prefix value does not match the road segment.	None
13.	Address number falls in a gap within the corresponding road ranges. This subcheck identifies when a street full name match is found, but the address number does not match any of the ranges; instead, it lies in a gap between the road's lowest and highest range. Example: For the same street full name, the ALI address number is 2000. The lowest road ranges are 11 - 17 and 12 - 16. The highest road ranges are 3900 - 3998 and 3901 - 3999. There is no road with ranges that cover the ALI address number 2000, so that record falls in a gap.	857

ALI to SSAP Synchronization Subchecks

The ALI to SSAP Synchronization QC subchecks are completed in the following order.

**Table 6**. ALI to SSAP quality control subchecks and exception codes.
Order	Subcheck Description	Exception Code
1.	Address number is missing or invalid. This subcheck searches for a valid ALI address number.	None
2.	No matching full street name found between the ALI record and the SSAP layer. This subcheck identifies when no street full name match is found.	None
3.	Address number from ALI record does not match any address point. This subcheck identifies when the ALI address number does not match any address point.	None
4.	Address only corresponds to an address point with a different ESN, but matching community. This subcheck identifies when an ALI record's ESN value does not match the corresponding address.	None
5.	Address only corresponds to an address point with a different community, but matching ESN. This subcheck identifies when an address point and ESN match is found, but only to records with mismatching Community values.	None
6.	Address only corresponds to an address point with a different community and ESN. This subcheck identifies when an ALI record's ESN and community values do not match the address point.	None
7.	Address AdNumPre value does not match the address point. This subcheck identifies when an ALI's address number prefix value does not match the address point.	None
8.	Address AdNumSuf value does not match the address point. This subcheck identifies when an ALI's address number suffix value does not match the address point.	None
9.	Address additional location value does not match the address point. This subcheck identifies when an ALI's additional location value does not match the address point.	None

SSAP to MSAG Synchronization Subchecks

The SSAP to MSAG Synchronization QC subchecks are completed in the following order.

**Table 7**. SSAP to MSAG quality control subchecks and exception codes.
Order	Subcheck Description	Exception Code
1.	Address number is missing or invalid. This subcheck searches for a valid address number.	None
2.	Address number fully matches multiple MSAG records. This subcheck searches for an address number that fully matches multiple MSAG records.—the address number, street full name, community, and ESN are an exact match.	None
3.	No matching full street name found between the address point and the MSAG record. This subcheck identifies when no full street name match is found.	None
4.	Address only corresponds to MSAG records with zero or missing ranges. This subcheck identifies when a street full name match is found, but only to MSAG records with zero, empty string, or null range values.	None
5.	Address number is lower than all corresponding MSAG ranges. This subcheck identifies when a street full name match is found, but only to MSAGs with address range values larger than the SSAP's address number.	None
6.	Address number is higher than all corresponding MSAG ranges. This subcheck identifies when a street full name match is found, but only to MSAGs with address range values smaller than the SSAP's address number.	None
7.	Address number parity does not match the corresponding MSAG records. This subcheck identifies when a street full name match is found, and the SSAP address number is within the MSAG's ranges, but only to MSAG records with the incorrect parity values.	None
8,	Address only corresponds to an MSAG record with a different ESN, but matching community. This subcheck identifies when an SSAP record's ESN value does not match the corresponding MSAG record.	None
9.	Address only corresponds to an MSAG record with a different community, but matching ESN. This subcheck identifies when an SSAP record's community value does not match the corresponding MSAG record.	None
10.	Address only corresponds to an MSAG record with a different community and ESN. This subcheck identifies when an SSAP record's ESN and community values do not match the corresponding MSAG record.	None
11.	SSAP records AdNumPre value does not match the MSAG record. This subcheck identifies when an SSAP's address number prefix value does not match the MSAG record.	None
12.	Address number falls in a gap within the corresponding road ranges. This subcheck identifies when a street full name match is found but the address number does not match any of the ranges; instead, it lies in a gap between the road's lowest and highest range.	None

SSAP to RCL Synchronization Subchecks

**Table 8**. SSAP to RCL quality control subchecks and exception codes.
Order	Subcheck Description	Exception Code
1.	Address number is missing (null) or invalid. This subcheck searches for a valid address number.	403
2.	Address number fully matches multiple road segments. This subcheck searches for an address number that fully matches multiple road segments—the address number, street full name, community, and ESN are an exact match.	413
3.	Address can be placed on both the left and right side of the corresponding road segment. This subcheck searches for an SSAP record's number that matches both the left and right side ranges of the corresponding roadcenterline—the address number, street full name, community, and ESN are an exact match.	412
4.	No matching full street name found between the address point and the road segment. This subcheck identifies when no full street name match is found.	404
5.	Address only corresponds to road segments with zero or missing ranges. This subcheck identifies when a street full name match is found, but only to roads with zero, empty string, or null range values.	405
6.	Address number is lower than all corresponding road ranges. This subcheck identifies when a street full name match is found, but only to roads with address range values larger than the SSAP's address number.	406
7.	Address number is higher than all corresponding road ranges. This subcheck identifies when a street full name match is found, but only to roads with address range values smaller than the SSAP's address number.	407
8.	Address number parity does not match the corresponding road segments. This subcheck identifies when a street full name match is found, and the SSAP address number is within the road's ranges, but only to road records with the incorrect parity values.	414
9,	Address only corresponds to a road segment with a different ESN, but matching community. This subcheck identifies when an SSAP record's ESN value does not match the corresponding road segment.	411
10.	Address only corresponds to a road segment with a different community, but matching ESN. This subcheck identifies when an SSAP record's community value does not match the corresponding road segment.	410
11.	Address only corresponds to a road segment with a different community and ESN. This subcheck identifies when an SSAP record's ESN and community values do not match the road corresponding segment.	409
12.	Address point's AdNumPre value does not match the road segment. This subcheck identifies when an SSAP's address number prefix value does not match the road segment.	None
13.	Address number falls in a gap within the corresponding road ranges. This subcheck identifies when a street full name match is found but the address number does not match any of the ranges; instead, it lies in a gap between the road's lowest and highest range.	408
14.	Unable to determine road segment's left and right side. This subcheck looks for addresses that cannot clearly be tied to one side of the corresponding road segment.	416
15.	Address falls on the wrong side of the road based on the road ranges. This subcheck looks for addresses that fall on the wrong side of the road based on its road ranges.	415
16.	Address number falls on the wrong block based on the road ranges. This subcheck looks for an address number that falls on the wrong block based on its road ranges.	417